With version 0.4, I wanted to make more of the thinking behind that system explicit, while beginning to turn those decisions into capabilities that can be used directly inside WordPress.

The idea has become central to how I think about the project:

Suede isn’t designed around a collection of styles. It’s designed around a system of decisions.

Version 0.4 is the first release where that idea becomes tangible in both the documentation and the theme itself.

DESIGN.md and design intelligence

The most important addition in Suede 0.4 might not be something you see in the WordPress editor.

Suede now ships with DESIGN.md, an intelligent source of truth for the design system. It defines not only the specifications behind Suede, but the reasoning that should guide how they are applied.

It covers the major parts of the system:

• Principles and composition
• Typography, color, layout, and spacing
• Shape, depth, interaction, and iconography
• Imagery, motion, responsive behavior, and accessibility

The distinction matters. A list of tokens can tell you which font size or spacing value is available. It cannot tell you what deserves attention, when to introduce contrast, why an image should carry more visual weight, or when subtraction is a better decision than adding another element.

DESIGN.md provides that context.

It also makes Suede more useful in AI-assisted design workflows. An agent can read the same design guidance a person can, giving it more context than it would get from inspecting theme.json, patterns, and CSS.

That is what I mean by design intelligence: making the decisions behind the system portable along with the system itself.

Expressive typography with Display

Version 0.4 also introduces Display, a new style variation built around the variable-width capabilities of Google Sans Flex.

Rather than introducing another typeface, Display extends the existing one across three distinct proportions for greater expressive range:

Standard remains the foundation. Condensed can introduce density, verticality, or greater scale within limited horizontal space. Expanded creates presence and horizontal scale for large editorial statements, numerals, pull quotes, and other moments that deserve more territory.

The widths are expressive tools, not alternate defaults.

One typeface. Three widths. One system.

Behind the scenes, I also optimized Google Sans Flex specifically for Suede. The original variable font was roughly 4 MB. The version shipping with Suede is approximately 200 KB while retaining the capabilities the system actually uses: weight, width, and slant.

There is something appropriately Suede about that: remove what isn’t necessary while making what remains more useful.

Extending Suede with the Icon block

Suede 0.4 also registers the Suede mark for use with the Icon block.

Previously, patterns using the mark treated the SVG as an image. Registering it through the Icon block API means the mark can now behave like an icon, with the controls and flexibility that come with the block.

It’s a small change, but it follows the same direction as Display: taking something that previously required a workaround and expressing it more naturally within WordPress.

That creates a useful filter for future development: identify the recurring design decisions Suede makes, then find the most natural way to express them within WordPress.

Where Suede goes next

A clearer progression is beginning to emerge for the project:

0.3 — Foundation
0.4 — Design intelligence
0.5 — Composition

Composition feels like the natural next problem to explore.

Suede already defines ideas around reading measure, wide composition, hierarchy, rhythm, negative space, scale, and relationships between typography and imagery. The interesting question is how to make more of that thinking tangible inside WordPress without turning Suede into a collection of rigid templates.

Suede 0.4 isn’t about adding more options. It’s about making the system more capable and the thinking behind it more explicit.

The goal isn’t to make Suede bigger. It’s to make the system smarter.

Reading Guide:

Intro | DTI Framework | Local Expertise | Building | Conclusion

Discovery has moved upstream

For decades, real estate marketing has focused on generating leads when buyers are ready to act. Phone calls, contact forms, and property inquiries measured success.

That assumption no longer reflects how people discover places.

One shift has become clear: real estate discovery has moved upstream.

Long before someone schedules a showing or contacts an agent, they research neighborhoods, compare communities, and decide where to live. Increasingly, those first impressions are formed through search engines, AI assistants, social media, and other digital touchpoints.

By the time a buyer reaches out, many of their decisions have already begun to take shape. This changes what it means to build authority.

People don’t search for agents; they search for place.

The agents who become the trusted source for understanding a place don’t simply generate more leads. They influence decisions before those leads even exist, and that’s where Place Authority comes in.

Rather than competing for attention only at the end of the buying journey, Place Authority shifts the focus from marketing properties to building the most complete, connected understanding of the places you serve.

Every article, neighborhood guide, market insight, community profile, and local resource contributes to a larger body of knowledge that helps people understand a place before they’re ready to decide.

The result isn’t simply greater visibility. It’s lasting authority built before the first conversation begins, and it compounds over time.

Place Authority: The DTI Framework

Place Authority is built on a simple progression. Each stage builds on the last, creating a strong foundation for lasting authority.

At the heart of Place Authority is this progression:

Discovery shapes how you’re found. Trust shapes what people believe. Influence shapes why you’re chosen.

Discovery

Discovery is how people find you and your knowledge. It begins long before someone is ready to buy or sell. Every neighborhood guide, market insight, community profile, and local resource creates an opportunity to be discovered.

Trust

Discovery creates the opportunity for trust. As people explore your work, they begin to recognize the depth, consistency, and usefulness of your expertise. Over time, that confidence grows into credibility.

Influence

Influence is the outcome of sustained discovery and trust. By the time someone reaches out, they already understand your perspective and value your expertise. The decision isn’t based solely on search results. It’s shaped by who has consistently helped them understand the place they’re exploring.

This progression reflects how authority is built today. Discovery opens the door. Trust strengthens the relationship. Influence shapes the decision.

Beyond local expertise

Every real estate professional has knowledge. The difference is that not every real estate professional becomes known for it.

Expertise alone doesn’t create authority. It has to be discoverable, understandable, and consistently reinforced over time. That’s the distinction between knowing a place and becoming its leading expert.

Place Authority isn’t about claiming expertise. It’s about earning recognition by helping people better understand the places they care about.

The professionals who build lasting authority aren’t simply answering questions. They’re creating the most complete, connected understanding of the places they serve.

Building Place Authority

Place Authority isn’t built through individual articles, but through a connected body of knowledge.

The model is simple: owned knowledge + distributed presence.

Owned knowledge is the foundation. Neighborhood guides, market insights, community profiles, local resources, and perspective accumulate into a body of work you control. Each contribution deepens understanding, strengthens connections, and compounds over time.

Distributed presence makes that knowledge visible. Search, AI assistants, LinkedIn, Instagram, email, and other channels extend its reach and create new paths back to the source.

Social isn’t where authority lives; it’s where authority becomes visible.

This distinction matters. The goal isn’t to build an audience on every platform. It’s to build something worth discovering, then distribute that knowledge wherever people are already exploring the places you serve.

Imagine a neighborhood guide connected to articles about local schools, parks, architecture, market trends, restaurants, history, and FAQs. Each page strengthens the others. Together, they become far more valuable than any single article could ever be on its own.

Every new insight adds context, and those connections create meaning.

Build a connected understanding of every place you serve.

Over time, those contributions compound into a trusted resource that helps people navigate a place with confidence.

There’s another reason this matters. As discovery increasingly moves through AI systems, the sources behind their answers become more important.

By systematically creating the most useful, structured, attributable body of knowledge about a place, you can become part of the information layer AI systems draw upon.

The goal isn’t simply to appear in the answer. It’s to become a source of the answer.

This is why Place Authority extends beyond publishing. Rather than asking, “What should I write next?” the better question becomes, “What understanding is still missing?”

Place Authority isn’t about publishing more.

It’s about becoming the leading expert by building the most complete, connected understanding of the places you serve.

The authority will follow.

A DESIGN.md file is a portable design specification that helps AI understand how a design system should look, feel, and behave.

Most design systems contain much of the information needed to create an interface: typography, colors, spacing, components, and styles. In WordPress, theme.json can define these decisions with considerable precision.

But implementation is not the same as intent.

A color value can tell AI which color to use. It cannot explain why that color exists, how prominently it should appear, or when another color would be appropriate. A spacing scale can provide values without explaining which relationships should feel tight and which should feel expansive.

Design requires judgment.

DESIGN.md attempts to make some of that judgment explicit. It describes the principles, constraints, and visual language behind a design system so AI does not have to infer them entirely from code or screenshots.

There is no established standard for a DESIGN.md file. I am exploring what one might look like and how it might function as AI becomes increasingly capable of designing and building digital experiences.

I recently added one to Suede, the design system behind my WordPress work and creative explorations. The distinction is quite simple: theme.json defines implementation; DESIGN.md defines intent.

View DESIGN.md on GitHub →

Principles

Suede begins with principles rather than tokens.

Before AI knows which font to use or how much space belongs between two elements, it should understand the broader ideas governing those decisions.

The DESIGN.md file establishes these rules:

Prefer fewer, stronger ideas. Decide what deserves attention and give it scale, weight, and room. Remove anything that weakens the message.

Hierarchy before decoration. Establish priority through type, spacing, form, and contrast. Let those elements work before adding anything more.

Space makes things matter. Give content enough room to breathe. Apply it with true purpose, not just for visual effect or unnecessary decoration.

Repetition creates coherence. Use consistent patterns to build familiarity and rhythm. Introduce variation only when the content calls for it.

Restraint, not minimalism. Be selective while preserving balance, character, and depth. Compositions should always feel confident and complete.

These principles establish the character before its visual properties.

That matters because AI can follow specifications too literally. Giving it every capability without the underlying philosophy can result in technically correct design that still feels wrong.

The goal is not to use everything Suede makes available, but to understand what makes something feel like Suede.

How to apply this system

A design specification needs to explain how its instructions should be interpreted. Otherwise, defaults can become rigid requirements and a small revision can turn into an unnecessary redesign.

Use this file to guide design decisions, including when generating or modifying an experience with AI. Apply explicit project requirements first, then Suede’s principles, then its defaults. Use expressive choices to adapt the defaults while preserving hierarchy, coherence, legibility, and purpose.

Treat the primary typeface, typography settings, palette, widths, spacing scale, and interface treatments as defaults. Expanded and condensed typography, accent typefaces, oversized display type, overlap, rounded geometry, and changes in visual mode are deliberate choices rather than automatic additions. Introduce them only when they serve a specific content or compositional need.

When modifying an existing experience, preserve its established decisions unless the request requires changing them. Resolve unspecified details through the existing system before introducing new treatments. Do not turn a local change into an unsolicited redesign.

This file defines design intent, not proof of an implementation. For WordPress work, inspect theme.json, style variations, registered block styles, patterns, and relevant assets before using named capabilities. Reuse existing presets and native controls where they support the intended result. Do not invent preset slugs, block styles, assets, or supported controls. If implementation differs from this guidance, identify the difference rather than silently changing the design specification or claiming a capability exists.

The order matters: project requirements first, principles second, defaults third. DESIGN.md should help AI make a relevant decision, then distinguish that decision from what the implementation actually supports.

Visual thesis

Before choosing components, AI should establish the idea that holds the composition together. Suede makes that step explicit:

Before building a new composition, establish a clear visual thesis appropriate to the subject, audience, content, location, and purpose. For an existing composition, identify its thesis before making changes.

Determine what should dominate, what should support it, what should create contrast or tension, what should repeat, where the composition should change visual mode, and what can be removed. Form a brief internal plan for these relationships before implementing sections. State the rationale when it helps review the work; do not require a separate approval step for routine design decisions.

Establish a visual world rather than treating a neutral canvas as the default. Decide how color fields, imagery, typography, and negative space should define the atmosphere of the experience. A composition may remain predominantly light, predominantly dark, image-led, or move between visual modes. Choose according to the subject and purpose rather than alternating treatments for variety.

Centered layouts, card grids, split compositions, and repeated section structures are valid when the content benefits from them. Do not select them automatically because they are familiar or easy to generate. Restraint does not require small typography, empty sections, or uniformly quiet composition.

This gives the design a direction before it has a layout. A centered hero or a card grid can be appropriate, but the content should earn that structure rather than inherit it by default.

Composition

A design system can easily become a collection of components.

Suede treats composition differently:

Every composition should have a clear visual priority. Establish what deserves attention first, then make supporting elements visibly subordinate. Where the experience requires action, make the primary next step easy to identify without giving every link equal prominence.

Use controlled contrast to create tension and hierarchy. Pair large with small, dense with open, image with type, and dominant with quiet. Restraint should limit competing ideas, not their scale.

Design relationships rather than assembling components. Begin with the relationship the content should create, then introduce only the elements needed to construct it. Do not place content in cards or bordered containers unless grouping, comparison, or interaction benefits from that structure.

Let important elements carry meaningful visual weight. Typography and imagery may become architectural elements within a composition. When something deserves presence, give it sufficient scale and territory while keeping supporting content readable and useful.

Allow elements to extend beyond the primary grid, overlap, layer, or share compositional space when doing so strengthens hierarchy, atmosphere, or visual relationships. Preserve legibility, access to controls, and a sensible reading order. Expressive positioning must have a workable narrow-screen treatment and must not produce unintended horizontal scrolling.

Create rhythm through repetition and change. Repeat structures to establish order, then vary them when the content requires a change in emphasis, pace, or mode. Avoid both mechanically identical sections and a new visual treatment for every section.

Before adding an element, determine whether hierarchy, typography, space, imagery, or contrast can accomplish the same purpose.

AI is already capable of assembling competent interfaces from familiar patterns. The harder problem is composition: understanding what deserves attention, establishing relationships between elements, and creating hierarchy without filling every available space.

That requires more than a component library.

Design system

Principles and composition establish intent. The design system translates that intent into a more concrete visual vocabulary.

This is where DESIGN.md begins to overlap with traditional design tokens, but with an important difference: values are accompanied by guidance about how they should be used.

Typography

Use Google Sans Flex as the primary typeface. Standard width is the default for body copy, navigation, controls, and most headings. Use variable width selectively to create contrast while preserving typographic continuity.

Use 110% expanded for large editorial statements, hero typography, numerals, pull quotes, and moments that benefit from greater presence and horizontal scale. Use 85% condensed when density or verticality strengthens the composition, particularly for oversized headlines, section markers, or narrow compositions.

Expanded and condensed widths are expressive tools, not alternate defaults or remedies for poorly fitted text. Keep sustained reading copy at standard width. Choose a consistent role for each expressive width rather than switching proportions arbitrarily.

A secondary or accent typeface may be introduced when it strengthens the subject or editorial character. Assign it a defined role, such as display headings or quotations, and preserve the primary face for supporting typography. Do not add typefaces solely to create variety.

Set body text at 18px, 400 weight, with a 1.75 line height. Headings default to 500 weight with no added letter spacing. Use 1.0 line height for display headings where the letterforms and wrapping remain clear; increase it for smaller or multiline reading headings when needed. Use 600 weight selectively for strong emphasis rather than as a default display weight.

Use the type scale 12, 14, 16, 18, 20, 24, 30, 36, 48, and 60px as the standard hierarchy. Sizes above 18px may scale fluidly with the viewport. Display type may exceed 60px when its role requires greater presence; treat this as an intentional extension, not a new default. Avoid arbitrary intermediate sizes when the existing scale establishes the relationship.

Keep supporting copy visibly subordinate without shrinking essential information into metadata. Reserve the smallest sizes for brief secondary information, not sustained reading.

Use uppercase text, 0.05em letter spacing, and 500 weight primarily for small navigation, labels, metadata, and eyebrows. Do not extend this treatment to long-form copy or prominent display typography.

Control wrapping through available width, type size, and balanced text where appropriate. Avoid isolated final words when they weaken the composition, but do not force desktop line breaks that become awkward on smaller screens. Keep heading semantics independent of visual size.

Apply -webkit-font-smoothing: antialiased and -moz-osx-font-smoothing: grayscale where supported, particularly for light text on dark backgrounds.

This is more useful to AI than simply declaring a font family and type scale.

Google Sans Flex provides continuity. Expressive widths and accent typefaces can strengthen a composition when they have a defined role, while sustained reading remains at standard width.

Color

Build primarily with black (#000000) and white (#ffffff). Use accent gold (#aa6600) for emphasis, interaction, rules, borders, and small moments of identity rather than as a dominant field color.

Use opacity variants of black and white (80%, 60%, 50%, 15%, 10%) and accent (80%, 60%, 50%, 20%, 10%) to establish hierarchy. Prefer tonal variation within the system over unrelated grays or secondary colors. Opacity is a compositional tool, not a guarantee of readable contrast; check the resulting color against its actual background.

Maintain strong contrast for primary and secondary text. Reserve low-contrast tones for nonessential borders, backgrounds, overlays, and subtle depth. Do not assume a muted preset is suitable for text on every surface.

Use Fade Down, Fade Up, Fade Right, or Fade Left when imagery needs contrast for overlaid content or controlled tonal depth. Choose the direction according to the text position and image. Check legibility across the entire text area and responsive crop rather than assuming the gradient is sufficient. Introduce another gradient only when these treatments cannot meet a specific functional need.

#aa6600 tells a machine what Suede’s accent color is. DESIGN.md explains its role: deliberate emphasis and small moments of identity rather than a dominant field color. It also asks AI to check contrast against the actual background.

Layout and spacing

Use three maximum widths according to content:

640px: Sustained reading and long-form text.

960px: Focused compositions combining text with supporting media.

1280px: Broad page compositions, navigation, grids, columns, and substantial imagery.

Treat 1280px as the primary composition width for page sections, not a requirement that every element fill it. Backgrounds may span the viewport while inner content generally sits within a centered container. Reading copy may retain its 640px measure within a wider composition. Do not constrain multi-column sections to the reading measure.

Maintain consistent horizontal page gutters using the project’s existing values. When no values exist, choose gutters from the spacing scale and reduce them deliberately as the viewport narrows. Containers must retain usable edge space before reaching their maximum width.

Use the spacing scale 20, 30, 40, 60, 80, and 100px for composition. Use smaller values to connect related elements and larger values to separate sections, ideas, or changes in visual mode. Major sections should usually receive more space than their internal relationships.

Compact interface gaps, icon-to-label spacing, and control padding may require values below 20px. Reuse the project’s existing compact spacing values; where none exist, establish a small consistent set rather than choosing a new value for each element.

Space must establish rhythm, focus, or hierarchy. Do not increase it merely to make a composition feel luxurious or minimal. Reduce large spacing on smaller screens while preserving the distinction between related content and separate sections.

The last rule is important.

“Use generous spacing” is easy for AI to interpret as “use more whitespace.” But whitespace without purpose can make a design feel empty.

The spacing values matter. The relationships they create matter more.

Responsive behavior

Responsive design should preserve the hierarchy of a composition rather than merely rearrange it.

Preserve hierarchy as the canvas narrows. Scale or simplify typography, spacing, imagery, and composition deliberately rather than mechanically collapsing the desktop layout.

Stack elements when their proportions or reading measure become compromised. Preserve a sensible document, reading, and keyboard order when changing visual arrangement. Remove or reduce offsets and overlaps before they obscure content or controls.

Give significant imagery a deliberate narrow-screen crop and focal point. Scale display type without crowding supporting content. Adapt navigation before labels become cramped or wrap unintentionally. Avoid fixed heights that clip content when text wraps or users enlarge it.

Review representative narrow, intermediate, and wide viewports, including widths between layout changes. A successful desktop composition does not establish responsive correctness.

DESIGN.md does not need to prescribe every breakpoint or responsive behavior. Those belong in implementation; instead, it should explain the intent and relationships that must survive as implementation changes.

Accessibility

Maintain readable contrast, legible typography, semantic headings, meaningful link text, accessible control names, and visible keyboard focus. Preserve access to content and controls when text is enlarged.

Provide text alternatives for informative imagery and treat purely decorative imagery accordingly. Do not use color, icons, hover, or motion as the sole means of conveying information or enabling an action.

Respect reduced-motion preferences. Accessibility should reinforce Suede’s clarity and restraint throughout the experience.

Shape and depth

Favor square, direct geometry for buttons, form controls, separators, and primary interface elements. Moderate or rounded geometry may be selected when it supports the subject or visual thesis. Treat that choice as part of the expression and apply it consistently within each control family; do not vary corners arbitrarily from element to element.

Use borders and rules sparingly, typically at 1px, to define structure. Avoid outlining every content group.

Treat shadows as accents, not ambient decoration. Suede’s shadow vocabulary includes a soft neutral shadow, a solid offset accent shadow, and a subtle offset accent shadow. Use verified project presets when an element needs separation or graphic emphasis. Avoid routine card shadows across the interface.

These rules discourage reaching reflexively for rounded cards, soft shadows, and familiar visual conventions simply because they are available. Geometry should support the subject and remain consistent within each control family.

Suede can use those techniques. It just needs a reason.

Interaction

Inline text links should remain visibly identifiable, normally through an underline. Navigation may use a consistent treatment appropriate to its context, with clear current and interactive states. Hover may shift toward the accent color where contrast remains readable.

Primary buttons use the accent color with white, uppercase small text, medium weight, and generous padding. Outline buttons use a transparent background with an accent border and text. On hover, filled buttons become transparent with an accent border and text, while outline buttons become accent-filled with white text. Choose square, moderate, or rounded corner geometry according to the composition and apply it consistently within the experience.

Check each button state against its actual background. On dark or image-led surfaces where the default treatment loses clarity, use black or white from the core palette to preserve contrast while retaining the same typography, padding, hover behavior, and corner geometry. Keep primary and secondary actions distinguishable.

Interactive feedback should be immediate but quiet. Prefer color and border changes; use restrained transforms only when they clarify interaction. Provide visible focus states and distinct active, selected, or disabled states where applicable. Do not make an essential action discoverable only on hover.

Interaction should reinforce the visual language rather than introduce a new one. The phrase I keep returning to is immediate but quiet: feedback should communicate state without becoming the experience itself.

Iconography

Use Google Material Symbols Sharp, with 200 weight and 48px optical size, for interface and supporting iconography. Optical size is the icon design setting, not a required rendered dimension. Choose displayed size according to the control or composition.

Use simple, recognizable symbols to clarify meaning, navigation, or interaction. Maintain consistent weight and treatment, using currentColor where appropriate. Do not add icons to every heading, feature, or list item for decoration. Give icon-only controls accessible names; hide decorative icons from assistive technology when adjacent text already provides their meaning.

Even a small choice like iconography can change the character and tone.

Imagery

Imagery carries substantial visual weight in Suede, so DESIGN.md gives it more direction than simply defining aspect ratios or image sizes.

Imagery should reinforce the subject, character, and purpose of the experience while carrying meaningful visual weight. Prefer fewer, substantial images over small decorative imagery.

Hero imagery may be full-width, contained, layered, or integrated into the composition. Choose the treatment according to the visual thesis rather than defaulting to a full-width Cover block. When overlaying text, select imagery and tonal treatments that preserve legibility across crops and viewport sizes.

Choose cropping, focal point, scale, and positioning according to the composition while preserving subject details essential to the content. Do not use imagery merely to fill space, and avoid embedding essential copy or controls inside images.

When generating imagery, favor grounded color, credible subjects, and tonal qualities that complement the system. Do not equate refinement with generic beige interiors, empty architecture, or stock luxury imagery regardless of the subject.

This becomes increasingly important when AI is responsible for both generating imagery and designing the interface around it.

“Use a large image” is not enough.

The image, crop, focal point, typography, contrast, and surrounding space are all part of the same composition.

Motion

Motion presents the same problem.

Telling AI to “use subtle animation” leaves substantial room for interpretation. Suede instead defines both the intent and the vocabulary:

Motion should reinforce hierarchy, focus, and interaction without calling attention to itself. Use the existing motion vocabulary to introduce content, clarify interaction, or add depth where appropriate. Do not animate every section automatically.

Use 250ms for quick interface transitions and 500ms for larger visual movement, with ease-out timing. For entrance motion, use a travel distance of approximately 30px. For image zoom on hover, use a scale of approximately 1.05 and contain the enlargement within the intended image area. Keep this zoom treatment on imagery rather than text or interface controls.

Content must remain available if entrance animation does not run. Disable or simplify nonessential movement when reduced motion is requested. Meaning, navigation, and interaction must survive with motion disabled.

Review

Design intent needs a review process. The current file asks AI to evaluate the result against the relationships it was meant to create.

Before delivering a new composition or meaningful revision, check the rendered result against these questions:

Is the primary visual priority clear, with supporting content visibly subordinate?

Do typography, imagery, and space express a coherent thesis rather than a generic template?

Do repeated elements behave consistently, with variation justified by content?

Do widths, spacing, and grouping communicate useful relationships?

Does the composition retain its intent across narrow, intermediate, and wide viewports?

Are text, controls, and every interaction state readable and accessible on their actual backgrounds?

Does the experience remain usable with keyboard input, enlarged text, and motion disabled?

Are referenced presets, assets, and capabilities verified in the implementation?

Can anything be removed without weakening meaning, function, or character?

When rendered verification is unavailable, distinguish design intent from verified behavior. Do not claim checks that were not performed.

Following the specification is not the same as verifying the result. A rendered review can reveal weak hierarchy, awkward wrapping, inaccessible controls, or spacing that looked reasonable in code. When that review is unavailable, AI should say so.

Application

The final section of Suede’s DESIGN.md may be the most important:

Treat these specifications as constraints, not templates. Preserve Suede’s visual character across subjects and media without forcing every composition into the same aesthetic. Interpret the system according to content, context, and medium. Variation should strengthen the composition rather than add novelty.

A useful design system should create coherence without producing sameness.

That becomes especially important with AI. If every instruction is interpreted as an absolute requirement, the system becomes a template. If every decision is optional, it stops being a system.

The goal is controlled freedom.

Suede establishes defaults, constraints, and principles while leaving enough room for a particular subject or identity to influence the result.

Design systems for humans and machines

Design systems have traditionally been expressed through artifacts created for humans and software. Designers use guidelines and libraries; developers use CSS, design tokens, components, and files like theme.json.

AI introduces another participant. It can read those artifacts, but reading an implementation and understanding the thinking behind it are different things.

That is the territory I am exploring with DESIGN.md: a lightweight layer that explains the design intelligence behind the system: what should dominate, what should remain quiet, and which relationships matter.

That is why DESIGN.md now lives at the root of Suede. The theme contains the implementation; DESIGN.md explains the intent.

Now Suede can tell AI not just what it is, but how it wants to be designed.

Reading Guide:

Intro | Approach | How It Builds | Designs | Who It’s For | Conclusion

What to know about Miles

AI is quickly changing how websites are designed and built, but much of what I’ve seen still treats design as an output: write a prompt, generate a website, and hope the result is good enough.

That approach has never been particularly interesting to me.

Miles, an AI design agent for WordPress, comes from longtime WordPress developer Andy Peatling and caught my attention because it approaches the problem differently. Rather than simply generating a website, Miles helps you explore ideas, establish a visual direction, and bring it to life in WordPress.

For designers and developers, that distinction matters.

How Miles handles WordPress design

Miles begins well before the website starts to take shape.

You can start with an idea, a brief, an existing website, or visual inspiration. From there, Miles helps establish the project direction and generates designs that can be explored and refined before committing to implementation.

In practical terms, Miles can help throughout the design process:

• Turn an idea or brief into a website direction.
• Explore multiple visual concepts before building.
• Refine typography, color, layout, and imagery.
• Design new pages or sections for an existing website.
• Convert an approved direction into WordPress.

This feels much closer to an actual design process than the one-shot generation that has defined many AI website builders.

Design is rarely about producing the first acceptable answer. It is about exploring possibilities, recognizing what works, and thoughtfully refining a direction until it feels right and complete.

Miles accelerates that process without removing you from it. AI provides speed and range, but taste and judgment remain important inputs.

How Miles builds with WordPress

The other significant distinction is what happens after a clear design direction has been established and approved.

Miles builds for WordPress using native components, including:

• Blocks and block patterns.
• Global styles and theme settings.
• Pages and navigation.
• Images and other media.
• Reusable design elements.

That matters because the output remains recognizable, editable WordPress rather than a proprietary layer sitting on top of it.

For someone who has spent years working with themes, blocks, patterns, and design systems, this is important.

The value of AI should not come at the expense of ownership or introduce another dependency that becomes difficult to remove later. The best tools should extend the platform rather than replace it.

Miles feels aligned with that philosophy. AI becomes part of the process, while WordPress remains the foundation.

Explore AI-powered WordPress design with Miles →

Turning ideas into WordPress designs

This is where Miles becomes especially interesting to me.

Building a website has traditionally placed a meaningful cost between having an idea and experiencing it as something real. Even a relatively simple direction can require design, development, configuration, and enough time that many ideas never move beyond imagination.

AI dramatically reduces that cost, making it possible to explore, refine, and turn an idea into a working WordPress website much faster than before.

Sienna Vale began as one of those explorations.

Miles helped inspire the initial direction, which I continued to refine and develop into a complete Suede child theme. What started as an AI-assisted concept became something tangible, useful, and ultimately worth pursuing.

Explore Sienna Vale: View the demo · Browse themes

That changes which ideas are worth pursuing in the first place.

I can explore directions I might previously have dismissed because they did not justify the effort required to build them. Some will work. Others will not. But discovering that becomes considerably less expensive.

This is where I think AI can have an enormous impact on creative work.

The advantage is not that we need fewer ideas. It is that we can afford to explore more of the good ones and see where they lead.

Who Miles is for and where it fits

Miles can be useful across a broad range of WordPress users, but I think its greatest value is leverage.

• Designers can explore and implement ideas with less friction.
• Developers can begin with a stronger visual direction.
• Agencies can accelerate concept development and production.
• Site owners can build sophisticated WordPress websites without code.

But Miles does not eliminate the need for expertise.

Complex functionality, integrations, accessibility, SEO, content strategy, and the countless details that separate a functional website from an exceptional one still require attention. Generated copy should be reviewed. Design decisions should be questioned. The finished work still needs someone willing to exercise judgment.

Miles does not replace designers or developers. It gives them leverage.

A different WordPress workflow

The fact that AI can build a website is quickly becoming unremarkable.

What interests me is what happens when AI becomes part of the creative process: helping us explore directions, challenge assumptions, iterate faster, and shorten the distance between an idea and something we can experience.

Miles offers an intriguing glimpse of that future while remaining grounded in WordPress. Perhaps that is the most compelling thing about it.

The result doesn’t make me want to build more websites with AI. It makes me want to pursue more ideas and see where they lead.

Explore AI-powered WordPress design with Miles →

Disclaimer: This article contains referral links. If you purchase Miles through one of these links, I may earn a commission at no additional cost to you.

Not because a mark defines the work, but because it creates a consistent point of recognition wherever the work appears across every medium.

That signature needed to feel as deliberate as the system it represents. It could not rely on decoration, symbolism, or stylistic effect. It needed to be simple, precise, and capable of becoming familiar through repeated use.

The result is the Suede mark.

Introducing the Suede mark

The Suede mark is constructed from a simple geometric system. It consists of two identical parallelograms within a 512 × 512 square. Each bar is 64 pixels wide with a 128-pixel gap. The mark is never stretched, rounded, or altered.

Every dimension is derived from the same underlying geometry. The system determines every proportion, leaving nothing to subjective refinement.

The mark remains consistent at every scale and in every context. Whether it appears as a favicon, a social avatar, or an embossed impression, its identity is defined by proportion rather than surface decoration.

A signature identity

The Suede mark is intentionally abstract. It does not depend on symbolism, metaphor, or hidden meaning to be immediately understood.

Its purpose is simpler: to identify Suede wherever it appears.

That restraint is intentional. Rather than asking to be interpreted, the Suede mark earns its meaning through repeated association with the product, the design system, and the work created with it. Like the imprint of a publisher, it becomes meaningful because of what it consistently accompanies.

It is less a symbol than a signature.

Designed to endure

Design trends change. Software evolves. Products mature.

A visual identity should outlast them all.

For that reason, the Suede mark is fixed. It is never stretched to fit, softened to follow trends, or unjustly modified for decoration. The same visual design appears everywhere, reinforcing recognition through consistency.

Its simplicity allows it to move between contexts without losing its character.

At small sizes, the mark remains unmistakably clear and easily recognizable. At larger scales, the underlying proportions become more apparent. In black, white, or gold, the mark is defined by form rather than effect.

That consistency carries across every application of design—whether used in favicons, site logos, documentation, social avatars, or watermarks.

A reflection of Suede

The mark reflects the same philosophy as the rest of Suede.

It favors geometry over ornament, consistency over novelty, and restraint over expression. Every relationship is intentional, and every dimension belongs to the system.

Like the product it represents, the mark is designed to support the work rather than compete with it. It creates recognition, then quietly recedes.

Reading Guide:

Introduction | Motion Styles | Motion Settings | Conclusion

Motion with purpose

The best motion feels natural. Rather than competing for attention, it should reinforce hierarchy, guide the eye, and create a smooth reading experience.

That’s the philosophy behind motion in Suede. Instead of offering a long list of animation effects, Suede includes a small set of subtle transitions designed to complement your content. The goal isn’t to impress readers with movement—it’s to help them stay focused on what they’re reading.

When used with restraint, motion becomes another design tool. Like typography, spacing, and editorial patterns, it helps create rhythm, establish relationships between elements, and make each page feel more polished without ever becoming a distraction.

Available motion styles

Motion in Suede includes two subtle animation effects designed to enhance the reading experience without distracting from your content. Each serves a different purpose while remaining intentionally subtle.

Fade In

Fade In Up

Like the motion styles themselves, the settings are intentionally simple. Rather than overwhelming with endless options, Suede provides the controls users need to create subtle, consistent animation throughout your site.

Motion settings

Once you’ve selected a motion style, Suede provides a small set of controls for fine-tuning how each animation behaves. The settings are intentionally focused, giving you enough flexibility to match the rhythm of your content without introducing unnecessary complexity.

Motion in Suede is currently supported in four core WordPress blocks: Group, Columns, Column, and Image. As the motion system evolves, support may expand to additional blocks.

Built into Suede

Motion is one of many design decisions that shape the experience of a website. When used with restraint, it reinforces hierarchy, guides attention, and helps content feel more natural to read.

In Suede, motion works alongside editorial patterns, typography, and spacing to create polished WordPress sites without demanding attention. Like every design decision, it exists to support the content—not compete with it.

The best animation is the kind readers barely notice.

Reading Guide:

Intro | Understanding | Discovery | Authority | Conclusion

A new way to think about content

For years, real estate marketing has measured success by how much content gets published. That’s the wrong metric.

The websites creating the most long-term value aren’t publishing more articles. They’re building something far more valuable.

I call this Knowledge Capital.

Every article becomes more valuable because of the ones around it.

What is Knowledge Capital?

Knowledge Capital is the accumulated value of a connected body of knowledge. Every new page adds context, strengthens relationships, and increases the authority of the whole. Instead of existing as isolated articles, each piece contributes to a resource that becomes more useful, more discoverable, and more authoritative over time.

This represents a shift in how authority is built online. Publishing is no longer about creating individual pages. It’s about creating knowledge that compounds with every thoughtful addition.

Place Authority explains why expertise should be rooted in the places you serve. The Real Estate Authority Principle explains how discovery, trust, and influence shape modern authority.

Knowledge Capital is the asset created when those ideas work together.

Content doesn’t compound

Most real estate websites are built around publishing. New articles are added over time, but they rarely strengthen the ones that came before. A market update stands on its own. A neighborhood guide exists in isolation. A buying checklist is published, then forgotten.

The result is an archive of disconnected pages rather than a growing body of expertise.

Publishing more content doesn’t automatically create more authority. It often creates more fragmentation. Each new article competes for attention instead of contributing to something larger.

That approach made sense when publishing itself was the competitive advantage. Today, the advantage belongs to professionals who build connected knowledge.

Knowledge compounds

Knowledge works differently than content.

A single article may answer one question, but a connected body of knowledge answers many. Every new page adds context, reinforces ideas, and creates pathways to discovery. The value of each page increases because it exists alongside related knowledge rather than in isolation.

Imagine an article about a neighborhood. Now imagine it connected to pages about its history, architecture, schools, parks, restaurants, market trends, and frequently asked questions. Together, they create a resource that is more valuable than any one page could become on its own.

Knowledge doesn’t grow because there are more pages. It grows because those pages strengthen one another.

That’s when publishing becomes something more than publishing.

Building Knowledge Capital

Knowledge Capital is built intentionally. It begins with choosing an area of expertise worth owning. For most real estate professionals, that expertise starts with the places they know best—the neighborhoods they serve, the market they understand, and the questions clients ask every day.

Expand it thoughtfully. Refine it regularly. Connect it wherever meaningful relationships exist.

Every new page should answer a question that leads to another. Every update should strengthen what has already been published. Every connection should make the body of knowledge more useful than it was before.

This is how local expertise becomes a lasting asset. Over time, each addition increases the value of the whole, creating an asset that is more discoverable, more trustworthy, and more difficult to replace.

Build an asset that compounds

The most valuable real estate websites won’t be the ones that publish the most content. They’ll be the ones that build the most valuable body of knowledge. That distinction will define the next generation of real estate marketing.

Instead of asking, “What should I publish next?”, ask, “What will strengthen the knowledge I’ve already built?”

That is how Knowledge Capital is created—one connected idea at a time.

Over time, a connected body of knowledge becomes more discoverable, more trusted, and more difficult to replace. It earns attention from buyers and sellers, provides lasting value to your market, and creates an enduring advantage that isolated content rarely achieves.

Build a body of knowledge. The authority you seek will follow.

Reading Guide:

Intro | Understanding | Discovery | Authority | Conclusion

A shift in how authority is built

For years, publishing rewarded individual pages. Write another article. Target another keyword. Add another page to the site. That was enough.

That approach worked because discovery happened one page at a time.

Today, the web is changing. Readers expect deeper context. Isolated content is losing leverage. Connected bodies of knowledge are gaining leverage. The advantage is shifting from more content to greater coherence.

I call this Structured Knowledge.

Authority is no longer built page by page. It is built through a connected body of knowledge—intentionally designed for understanding, structured for discovery, and published for authority.

This is the shift I’m exploring because I believe it will define how lasting authority is built—not for the next decade, but for the future of publishing.

Design for understanding

Most websites are designed to publish information. Far fewer are designed to help people understand it.

Understanding doesn’t happen by accident. It emerges through thoughtful decisions about hierarchy, spacing, typography, emphasis, and sequence. Each element reduces friction, helping readers move through ideas with greater clarity and confidence.

Good design doesn’t compete for attention. It directs it.

That’s why I think of design as more than aesthetics. It’s an editorial tool. It reveals relationships between ideas, creates moments of emphasis, and helps readers recognize what matters most. When design disappears into the reading experience, understanding becomes effortless.

Five principles of understanding

• Reduce cognitive load.
• Create a visual hierarchy.
• Reveal relationships.
• Emphasize what matters.
• Reward deep reading.

Good design helps readers understand one idea. Lasting authority comes from helping them navigate many. That’s where structure becomes essential.

Structure for discovery

A single page can communicate an idea. A connected body of knowledge reveals how ideas relate to one another.

Structure transforms individual pages into something greater. It creates pathways that guide readers from one concept to the next, helping them explore topics with context rather than in isolation. The result is a reading experience that feels intentional instead of fragmented.

Discovery is no longer about finding a page. It’s about understanding where that page belongs within a larger body of knowledge.

Connect ideas

Each article should build on the ideas that came before it. That means linking related concepts, building on previous work, and using consistent language that helps readers recognize patterns over time. Knowledge becomes more valuable when each new idea reinforces the ones that came before it.

Create pathways

Readers rarely start at the beginning. They enter from search, social media, recommendations, or AI-generated summaries. Structure helps orient them, discover related ideas, and continue exploring beyond a single page.

Build systems

Authority is no longer built at the page level. It is built at the system level.

A connected body of knowledge becomes easier to navigate, easier to understand, and ultimately easier to trust. That’s the role of structure: not to organize content for its own sake, but to create a body of knowledge that compounds in value over time.

Together, they create a simple progression: Design shapes understanding. Structure shapes discovery. Publishing shapes authority.

Every new article should strengthen the ideas around it. Over time, individual pages become a connected body of knowledge—one that grows more valuable with every new insight, connection, and contribution.

That’s how knowledge compounds. And that’s how authority is built.

Publish for authority

Publishing has never been easier. Building authority has never been harder.

The difference isn’t how often you publish. It’s what each new article contributes to the body of knowledge you create. Every page should deepen understanding, strengthen connections, and reinforce what already exists.

Publishing isn’t the destination. It’s the mechanism through which knowledge grows over time.

Knowledge compounds. Each new article adds context, and each new connection creates meaning. Together, they form something more valuable than isolated content ever could: a resource readers rely on.

When publishing is guided by understanding and supported by structure, authority becomes the natural outcome. Not because one page succeeded, but because every page contributed to something larger.

Conclusion

The future of publishing won’t be defined by who creates the most content. It will be defined by who builds the clearest body of knowledge.

That requires a different way of thinking. Design is no longer just about presentation. Structure is no longer just about organization. And publishing is no longer just about producing more pages.

This is why I’m exploring Structured Knowledge.

Not as a framework or methodology, but as a philosophy for building a connected body of knowledge—one designed for understanding, structured for discovery, and published for authority.

Because authority isn’t built one page at a time.

It’s built one idea, one connection, and one contribution at a time.

Reading Guide:

Google Sans | Editorial Design | My Choice

Understanding Google Sans

Google Sans is a contemporary sans-serif typeface developed by Google for its visual identity. While many recognize it from Google’s logo and products like Gmail, Docs, and Calendar, it represents far more than branding.

Designed specifically for digital environments, Google Sans combines clarity, flexibility, and consistency in a way that feels equally at home in user interfaces, editorial layouts, and long-form articles. Its restrained personality allows the content—not the typography—to remain the focus.

Before explaining why I chose Google Sans as the foundation of Suede, it’s worth understanding what makes the typeface distinctive.

A brief history

Google Sans emerged from Google’s effort to create a unified typographic system across its growing ecosystem of products. Rather than relying on an existing commercial typeface, Google developed a family that could reflect its design language while meeting the demands of modern digital interfaces.

The typeface became widely recognizable with Google’s refreshed visual identity, but it has continued to evolve beyond the company’s logo. Today, it appears throughout Google’s products and services, creating consistency across a wide range of experiences.

Design philosophy

Google Sans balances precision with approachability. It feels contemporary without being trendy, geometric without becoming rigid, and expressive without distracting from the content it presents.

Rather than drawing attention to itself, the typeface is designed to support reading. Its proportions, spacing, and rhythm create a calm, familiar user experience that adapts naturally across headings, interfaces, and body text.

Readability on the web

Typography has one primary responsibility: helping people understand what they’re reading, with clarity and without distraction.

Google Sans performs exceptionally well on screens because it was designed with digital reading in mind. Open letterforms, comfortable spacing, and balanced proportions contribute to a reading experience that feels effortless across a wide range of devices and text sizes.

Those qualities become even more important in long-form publishing, where subtle typographic decisions can influence how comfortably readers engage with an idea over time, from the opening sentence to the final paragraph.

Variable font capabilities

One of Google Sans’s greatest strengths is its availability as a variable font. Instead of relying on separate font files for every style, a single variable font provides continuous control across multiple design axes.

For Google Sans, those include weight, width, and rounded styles, making it flexible while preserving a consistent visual voice. In practice, Suede primarily relies on the weight axis to create hierarchy throughout the system.

These capabilities allow designers to create hierarchy and emphasis without introducing additional typefaces. Rather than switching fonts to create contrast, Google Sans offers a typographic system within a single family.

See the official Google Sans specimen for the full range of styles.

Design characteristics

Google Sans isn’t memorable because of any single feature. It’s memorable because dozens of thoughtful design decisions work together.

Its proportions feel generous without becoming loose. Its rhythm remains even across different sizes and weights. And its overall personality is confident without feeling cold or overly expressive.

Those qualities make Google Sans particularly well-suited to editorial experiences, where typography should quietly support understanding rather than competing for attention.

Typography in editorial design

Typography is often treated as a visual decision, but its greatest influence is editorial. Before readers absorb a single idea, they experience the typography that presents it. Every choice—from size and weight to spacing and hierarchy—shapes how comfortably information can be understood.

Good typography doesn’t compete with the content. It reduces friction, establishes rhythm, and creates a reading experience that feels effortless. The best typography is often the typography readers never notice.

Many websites combine multiple typefaces to create visual variety. I’ve increasingly come to believe the opposite approach is stronger.

One thoughtfully designed typeface with a broad range of capabilities can provide all the hierarchy and flexibility most editorial experiences require, while creating a more cohesive visual language.

That philosophy extends beyond typography itself. Design isn’t simply about making information attractive—it’s about making information easier to navigate. When typography supports the content instead of distracting from it, readers are free to focus on the ideas rather than the design.

Why I chose Google Sans

Every design system begins with a handful of foundational decisions.

For Suede, typography was one of the first. After exploring countless types over the years, I kept returning to Google Sans—not because it was familiar, but because it aligned with the reading experience I wanted to create.

What ultimately drew me to Google Sans wasn’t any single feature, but its balance. Contemporary yet refined, the font remains flexible enough to accommodate both interfaces and long-form editorial content.

One thoughtfully designed type family simplifies every decision that follows. Hierarchy comes from weight. Personality comes from composition. Every typographic decision speaks with the same, consistent voice.

That philosophy extends naturally into Suede. I believe good design should make ideas easier to understand, not simply more attractive to look at. Typography establishes the foundation, while Editorial Patterns provide structure, hierarchy, and orientation throughout the reading experience.

Google Sans wasn’t the only typeface I considered. It was simply the one that best reflected the values I wanted Suede to embody: clarity, consistency, restraint, and a quiet confidence that allows the content to remain the focus.

If I were starting Suede again today, I’d make the same decision.

Reading Guide:

Intro | Definitions | Key Idea | Perspective | Sequence | Statistic

A better reading experience

Most conversations about digital publishing and WordPress focus on creating content. Others focus on presenting it through typography, layout, color, and spacing. These disciplines matter, but they don’t fully explain why some long-form content is easier to understand than others.

Between the words themselves and the surrounding visual design lies another layer—one shaped by structure, emphasis, and orientation. It helps readers recognize important ideas, establish shared terminology, navigate complex topics, and maintain context throughout.

These recurring design elements appear across essays, documentation, books, and other forms of publishing like WordPress. Individually, each serves a specific purpose. Together, they create a better reading experience.

I call them Editorial Patterns.

Editorial Patterns are recurring design elements that provide structure, improve understanding, and guide readers through complex ideas. Rather than relying solely on paragraphs, they introduce moments of clarity that guide attention without interrupting the narrative.

This article defines Editorial Patterns, outlines their core principles, and establishes a shared foundation for the ideas that follow.

Definitions

Every discipline depends on common language. Before readers can understand new ideas, they need confidence that the words being used carry a clear and consistent meaning.

Definitions create that foundation. Rather than assuming familiarity, they introduce important terminology early, reducing ambiguity and creating a common point of reference for everything that follows.

With WordPress, this pattern is especially valuable when introducing original concepts, specialized language, or ideas that benefit from greater precision. By defining key terms before expanding on them, readers spend less time interpreting language and more time engaging with ideas.

Example

The following example demonstrates how Definitions establish a common language for the ideas explored throughout this collection.

A well-designed set of definitions does more than clarify terminology. Together, they create the foundation on which meaningful ideas can grow.

Shared language creates shared understanding.

Key Idea

Not every idea deserves equal attention. Some ideas shape everything that follows and should be impossible for readers to miss.

A Key Idea isolates the central insight of an article, giving readers a natural place to pause and consider its meaning. Without interrupting the narrative, it reinforces the idea that matters most.

A Key Idea is particularly effective in long-form articles, where readers often skim, revisit specific sections, or return later. By emphasizing the most important idea in an article, it creates a memorable anchor that improves understanding long after the final paragraph.

Example

The following example demonstrates how a Key Idea emphasizes an important insight without interrupting the flow of reading.

A well-designed Key Idea does more than emphasize an important sentence. It reinforces the idea readers are most likely to remember.

What readers remember shapes what they understand.

Perspective

A fact explains what something is. Perspective helps readers understand why it matters by placing it within a broader context of connected ideas.

A Perspective introduces context that broadens, challenges, or reframes an idea. Rather than adding more information, it changes the lens through which readers interpret the information they already have.

Perspective is especially valuable when introducing original thinking, questioning common assumptions, or connecting ideas across disciplines. A well-placed Perspective encourages readers to consider a concept from a different angle without disrupting the narrative.

Example

The following example demonstrates how Perspective broadens an idea through additional context and a different point of view.

A well-crafted Perspective does more than add context. It invites readers to see familiar ideas in a new way and consider their broader implications.

How we frame ideas influences how they’re understood.

Sequence

Some ideas are best understood as a progression rather than a collection of individual points. A Sequence reveals how one idea leads naturally to the next, helping readers recognize cause, connection, and momentum.

Rather than presenting concepts in isolation, a Sequence organizes them into a clear path. This makes complex frameworks easier to understand and gives readers a simple mental model they can remember after they finish reading.

This pattern is especially valuable when explaining original frameworks, recurring processes, or relationships that unfold over time. Making progression visible helps readers understand not only what the ideas are but also how they fit together.

Example

The following example demonstrates how a Sequence reveals the relationship between connected ideas and the progression they create.

A well-crafted Sequence does more than organize information. It reveals the progression that gives individual ideas greater meaning.

Understanding grows when relationships become visible.

Statistic

Ideas become more convincing when they’re supported by profound research. A carefully chosen statistic reinforces an important point, giving readers greater confidence in the ideas being presented.

Instead of overwhelming readers with numbers, a Statistic highlights a single piece of meaningful evidence that strengthens the surrounding narrative. Used thoughtfully, it adds credibility without distraction.

Statistics are especially effective when introducing research, supporting an argument, or demonstrating the significance of an idea.

A well-placed Statistic transforms evidence into confidence by giving readers a reason to trust what they’re reading and why it matters.

Example

The following example demonstrates how a Statistic reinforces an important idea through a single, carefully chosen data point.

A well-crafted Statistic does more than present data. It gives important ideas greater credibility through evidence that readers can trust and understand.

What readers remember shapes what they trust.

An evolving framework

Editorial Patterns are not intended to be a fixed collection. As new patterns emerge and others become more refined, this work will continue to evolve.

The objective is not to create a definitive list of patterns. It is to establish a common language and a practical framework for recognizing the recurring design elements that improve understanding, provide structure, and help readers navigate long-form content.

Suede explores these ideas in WordPress through a growing collection of reusable Editorial Patterns that bring this philosophy to life.

Every framework begins with a definition. This is only the beginning.